Network coding with dynamic redundancy overhead

ABSTRACT

Methods, systems, and devices for wireless communications are described. In some wireless communications systems, a base station may transmit sets of network coding encoded packets user equipments (UEs), and each set of network coding encoded packets may be associated with a redundancy overhead. The base station may dynamically identify the redundancy overhead for transmitting sets of network coding encoded packets to each UE based on a failure rate associated with a previous transmission of network coding encoded packets to that UE. For example, the base station may determine a failure rate associated with a transmission of a first set of network coding encoded packets and may identify a redundancy overhead associated with one or more second sets of network coding encoded packets based on the determined failure rate. In some cases, the base station may identify different redundancy overheads for transmissions of network coding encoded packets to different UEs.

FIELD OF TECHNOLOGY

The following relates to wireless communications, including networkcoding with dynamic redundancy overhead.

BACKGROUND

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude one or more base stations or one or more network access nodes,each simultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support network coding with dynamic redundancyoverhead. Generally, the described techniques provide for a base stationto use a redundancy overhead for transmitting sets of network codingencoded packets based on a channel quality associated with thetransmission. That is, a base station may transmit a set of networkcoding encoded packets to a user equipment (UE) and determine a failurerate associated with that transmission. For example, the base stationmay identify the failure rate based on receiving, from the UE, feedback(e.g., hybrid automatic repeat request (HARQ) negative acknowledgement(NACK) feedback), a retransmission request (e.g., a radio link control(RLC) status report message), or an indication of the failure rate.After determining the failure rate, the base station may identify aredundancy overhead for future transmissions of sets of network codingencoded packets to the UE based on the determined failure rate. The basestation may then transmit additional sets of network coding encodedpackets using the identified redundancy overhead. In cases that the basestation is in communication with multiple UEs, the base station mayidentify different redundancy overhead for communications with each UEbased on a failure rate associated with transmissions to each respectiveUE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure.

FIGS. 3 and 4 illustrate example process flows that support networkcoding with dynamic redundancy overhead in accordance with aspects ofthe present disclosure.

FIG. 5 illustrates an example of protocol stack functions that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

FIGS. 6 and 7 show block diagrams of devices that support network codingwith dynamic redundancy overhead in accordance with aspects of thepresent disclosure.

FIG. 8 shows a block diagram of a communications manager that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

FIG. 9 shows a diagram of a system including a device that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

FIGS. 10 and 11 show block diagrams of devices that support networkcoding with dynamic redundancy overhead in accordance with aspects ofthe present disclosure.

FIG. 12 shows a block diagram of a communications manager that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

FIG. 13 shows a diagram of a system including a device that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

FIGS. 14 through 17 show flowcharts illustrating methods that supportnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure.

DETAILED DESCRIPTION

In some wireless communication systems, a base station (or othertransmitting device such as a user equipment (UE) or an integratedaccess and backhaul (IAB) node) may perform network coding of radio linkcontrol (RLC) layer packets. The network coding may be used to encode afirst number of packets of an RLC service data unit (SDU) into a secondnumber of packets of an RLC protocol data unit (PDU) that may then betransmitted (e.g., following medium access control (MAC) and physical(PHY) layer processing) to a UE (or other receiving device). The UE maydecode the RLC PDU using network coding techniques, which may allow forrecovery of one or more missing packets.

In some cases, the base station may transmit a set of network codingencoded packets (e.g., of the RLC PDU) with an associated redundancyoverhead. That is, a portion of the set of network coding encodedpackets may include redundant data. In some cases, this may enable theUE to decode the set of network coding encoded packets even in cases ofone or more missing packets. In some systems, the base station may be incommunication with multiple UEs and may utilize a same redundancyoverhead for unicast transmissions to each of the UEs. However, aquantity of redundant network coding encoded packets (e.g., a redundancyoverhead) necessary to achieve reliable communications with a UE may bebased on a channel quality associated with that UE. For example, incases that a channel quality associated with communications between abase station and a UE is relatively high, the UE may be able tosuccessfully receive the set of network coding encoded packets having arelatively low redundancy overhead. Additionally, in cases that thechannel quality associated with communications between the base stationand the UE is relatively low (e.g., resulting in a higher failure rate),the UE may rely on a higher redundancy overhead to successfully recoverone or more missing packets. Therefore, utilizing a same redundancyoverhead for unicast transmissions to UEs that may not have similarchannel qualities may result in excessive redundancy overhead orinsufficient redundancy overhead for transmissions with some UEs.

In the example of wireless communication systems as disclosed herein, abase station may use a dynamic redundancy overhead for unicasttransmissions to different UEs. This may enable the base station todecrease unnecessary overhead for transmissions with UEs associated withhigher channel qualities while still maintaining reliable communicationswith UEs associated with lower channel qualities. For example, the basestation may determine a failure rate associated with a transmission toeach UE and the base station may identify a redundancy overhead fortransmissions with each UE based on the identified failure rate. Theredundancy overhead updates may be base station-initiated orUE-initiated (e.g., the base station may update the redundancy overheadbased on receiving a request for the updated redundancy overhead fromthe UE). In one case, the redundancy overhead updates may be based on aperiodicity for redundancy overhead updates. In another case, theredundancy overhead updates may be based on the identified failure rate.That is, the base station may update the redundancy overhead in casesthat the identified failure rate exceeds a threshold failure rate.

Aspects of the disclosure are initially described in the context ofwireless communications systems. Aspects of the disclosure are thendescribed in the context of process flows and Aspects of the disclosureare further illustrated by and described with reference to apparatusdiagrams, system diagrams, and flowcharts that relate to network codingwith dynamic redundancy overhead.

FIG. 1 illustrates an example of a wireless communications system 100that supports network coding with dynamic redundancy overhead inaccordance with aspects of the present disclosure. The wirelesscommunications system 100 may include one or more base stations 105, oneor more UEs 115, and a core network 130. In some examples, the wirelesscommunications system 100 may be a Long Term Evolution (LTE) network, anLTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR)network. In some examples, the wireless communications system 100 maysupport enhanced broadband communications, ultra-reliable (e.g., missioncritical) communications, low latency communications, communicationswith low-cost and low-complexity devices, or any combination thereof.

The base stations 105 may be dispersed throughout a geographic area toform the wireless communications system 100 and may be devices indifferent forms or having different capabilities. The base stations 105and the UEs 115 may wirelessly communicate via one or more communicationlinks 125. Each base station 105 may provide a coverage area 110 overwhich the UEs 115 and the base station 105 may establish one or morecommunication links 125. The coverage area 110 may be an example of ageographic area over which a base station 105 and a UE 115 may supportthe communication of signals according to one or more radio accesstechnologies.

The UEs 115 may be dispersed throughout a coverage area 110 of thewireless communications system 100, and each UE 115 may be stationary,or mobile, or both at different times. The UEs 115 may be devices indifferent forms or having different capabilities. Some example UEs 115are illustrated in FIG. 1. The UEs 115 described herein may be able tocommunicate with various types of devices, such as other UEs 115, thebase stations 105, or network equipment (e.g., core network nodes, relaydevices, integrated access and backhaul (IAB) nodes, or other networkequipment), as shown in FIG. 1.

The base stations 105 may communicate with the core network 130, or withone another, or both. For example, the base stations 105 may interfacewith the core network 130 through one or more backhaul links 120 (e.g.,via an S1, N2, N3, or other interface). The base stations 105 maycommunicate with one another over the backhaul links 120 (e.g., via anX2, Xn, or other interface) either directly (e.g., directly between basestations 105), or indirectly (e.g., via core network 130), or both. Insome examples, the backhaul links 120 may be or include one or morewireless links.

One or more of the base stations 105 described herein may include or maybe referred to by a person having ordinary skill in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or agiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or other suitable terminology.

A UE 115 may include or may be referred to as a mobile device, awireless device, a remote device, a handheld device, or a subscriberdevice, or some other suitable terminology, where the “device” may alsobe referred to as a unit, a station, a terminal, or a client, amongother examples. A UE 115 may also include or may be referred to as apersonal electronic device such as a cellular phone, a personal digitalassistant (PDA), a tablet computer, a laptop computer, or a personalcomputer. In some examples, a UE 115 may include or be referred to as awireless local loop (WLL) station, an Internet of Things (IoT) device,an Internet of Everything (IoE) device, or a machine type communications(MTC) device, among other examples, which may be implemented in variousobjects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with varioustypes of devices, such as other UEs 115 that may sometimes act as relaysas well as the base stations 105 and the network equipment includingmacro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations,among other examples, as shown in FIG. 1.

The UEs 115 and the base stations 105 may wirelessly communicate withone another via one or more communication links 125 over one or morecarriers. The term “carrier” may refer to a set of radio frequencyspectrum resources having a defined physical layer structure forsupporting the communication links 125. For example, a carrier used fora communication link 125 may include a portion of a radio frequencyspectrum band (e.g., a bandwidth part (BWP)) that is operated accordingto one or more physical layer channels for a given radio accesstechnology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layerchannel may carry acquisition signaling (e.g., synchronization signals,system information), control signaling that coordinates operation forthe carrier, user data, or other signaling. The wireless communicationssystem 100 may support communication with a UE 115 using carrieraggregation or multi-carrier operation. A UE 115 may be configured withmultiple downlink component carriers and one or more uplink componentcarriers according to a carrier aggregation configuration. Carrieraggregation may be used with both frequency division duplexing (FDD) andtime division duplexing (TDD) component carriers.

Signal waveforms transmitted over a carrier may be made up of multiplesubcarriers (e.g., using multi-carrier modulation (MCM) techniques suchas orthogonal frequency division multiplexing (OFDM) or discrete Fouriertransform spread OFDM (DFT-S-OFDM)). In a system employing MCMtechniques, a resource element may consist of one symbol period (e.g., aduration of one modulation symbol) and one subcarrier, where the symbolperiod and subcarrier spacing are inversely related. The number of bitscarried by each resource element may depend on the modulation scheme(e.g., the order of the modulation scheme, the coding rate of themodulation scheme, or both). Thus, the more resource elements that a UE115 receives and the higher the order of the modulation scheme, thehigher the data rate may be for the UE 115. A wireless communicationsresource may refer to a combination of a radio frequency spectrumresource, a time resource, and a spatial resource (e.g., spatial layersor beams), and the use of multiple spatial layers may further increasethe data rate or data integrity for communications with a UE 115.

The time intervals for the base stations 105 or the UEs 115 may beexpressed in multiples of a basic time unit which may, for example,refer to a sampling period of T_(s)=1/(Δf_(max)·N_(f)) seconds, whereΔf_(max) may represent the maximum supported subcarrier spacing, andN_(f) may represent the maximum supported discrete Fourier transform(DFT) size. Time intervals of a communications resource may be organizedaccording to radio frames each having a specified duration (e.g., 10milliseconds (ms)). Each radio frame may be identified by a system framenumber (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes orslots, and each subframe or slot may have the same duration. In someexamples, a frame may be divided (e.g., in the time domain) intosubframes, and each subframe may be further divided into a number ofslots. Alternatively, each frame may include a variable number of slots,and the number of slots may depend on subcarrier spacing. Each slot mayinclude a number of symbol periods (e.g., depending on the length of thecyclic prefix prepended to each symbol period). In some wirelesscommunications systems 100, a slot may further be divided into multiplemini-slots containing one or more symbols. Excluding the cyclic prefix,each symbol period may contain one or more (e.g., N_(f)) samplingperiods. The duration of a symbol period may depend on the subcarrierspacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallestscheduling unit (e.g., in the time domain) of the wirelesscommunications system 100 and may be referred to as a transmission timeinterval (TTI). In some examples, the TTI duration (e.g., the number ofsymbol periods in a TTI) may be variable. Additionally or alternatively,the smallest scheduling unit of the wireless communications system 100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using one or more oftime division multiplexing (TDM) techniques, frequency divisionmultiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A controlregion (e.g., a control resource set (CORESET)) for a physical controlchannel may be defined by a number of symbol periods and may extendacross the system bandwidth or a subset of the system bandwidth of thecarrier. One or more control regions (e.g., CORESETs) may be configuredfor a set of the UEs 115. For example, one or more of the UEs 115 maymonitor or search control regions for control information according toone or more search space sets, and each search space set may include oneor multiple control channel candidates in one or more aggregation levelsarranged in a cascaded manner. An aggregation level for a controlchannel candidate may refer to a number of control channel resources(e.g., control channel elements (CCEs)) associated with encodedinformation for a control information format having a given payloadsize. Search space sets may include common search space sets configuredfor sending control information to multiple UEs 115 and UE-specificsearch space sets for sending control information to a specific UE 115.

In some examples, a base station 105 may be movable and thereforeprovide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas 110associated with different technologies may overlap, but the differentgeographic coverage areas 110 may be supported by the same base station105. In other examples, the overlapping geographic coverage areas 110associated with different technologies may be supported by differentbase stations 105. The wireless communications system 100 may include,for example, a heterogeneous network in which different types of thebase stations 105 provide coverage for various geographic coverage areas110 using the same or different radio access technologies.

The wireless communications system 100 may be configured to supportultra-reliable communications or low-latency communications, or variouscombinations thereof. For example, the wireless communications system100 may be configured to support ultra-reliable low-latencycommunications (URLLC) or mission critical communications. The UEs 115may be designed to support ultra-reliable, low-latency, or criticalfunctions (e.g., mission critical functions). Ultra-reliablecommunications may include private communication or group communicationand may be supported by one or more mission critical services such asmission critical push-to-talk (MCPTT), mission critical video (MCVideo),or mission critical data (MCData). Support for mission criticalfunctions may include prioritization of services, and mission criticalservices may be used for public safety or general commercialapplications. The terms ultra-reliable, low-latency, mission critical,and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may also be able to communicate directly withother UEs 115 over a device-to-device (D2D) communication link 135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115utilizing D2D communications may be within the geographic coverage area110 of a base station 105. Other UEs 115 in such a group may be outsidethe geographic coverage area 110 of a base station 105 or be otherwiseunable to receive transmissions from a base station 105. In someexamples, groups of the UEs 115 communicating via D2D communications mayutilize a one-to-many (1:M) system in which each UE 115 transmits toevery other UE 115 in the group. In some examples, a base station 105facilitates the scheduling of resources for D2D communications. In othercases, D2D communications are carried out between the UEs 115 withoutthe involvement of a base station 105.

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC) or 5G core (5GC), which may include at leastone control plane entity that manages access and mobility (e.g., amobility management entity (MME), an access and mobility managementfunction (AMF)) and at least one user plane entity that routes packetsor interconnects to external networks (e.g., a serving gateway (S-GW), aPacket Data Network (PDN) gateway (P-GW), or a user plane function(UPF)). The control plane entity may manage non-access stratum (NAS)functions such as mobility, authentication, and bearer management forthe UEs 115 served by the base stations 105 associated with the corenetwork 130. User IP packets may be transferred through the user planeentity, which may provide IP address allocation as well as otherfunctions. The user plane entity may be connected to IP services 150 forone or more network operators. The IP services 150 may include access tothe Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or aPacket-Switched Streaming Service.

Some of the network devices, such as a base station 105, may includesubcomponents such as an access network entity 140, which may be anexample of an access node controller (ANC). Each access network entity140 may communicate with the UEs 115 through one or more other accessnetwork transmission entities 145, which may be referred to as radioheads, smart radio heads, or transmission/reception points (TRPs). Eachaccess network transmission entity 145 may include one or more antennapanels. In some configurations, various functions of each access networkentity 140 or base station 105 may be distributed across various networkdevices (e.g., radio heads and ANCs) or consolidated into a singlenetwork device (e.g., a base station 105).

The wireless communications system 100 may operate using one or morefrequency bands, typically in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band because thewavelengths range from approximately one decimeter to one meter inlength. The UHF waves may be blocked or redirected by buildings andenvironmental features, but the waves may penetrate structuressufficiently for a macro cell to provide service to the UEs 115 locatedindoors. The transmission of UHF waves may be associated with smallerantennas and shorter ranges (e.g., less than 100 kilometers) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

The wireless communications system 100 may utilize both licensed andunlicensed radio frequency spectrum bands. For example, the wirelesscommunications system 100 may employ License Assisted Access (LAA),LTE-Unlicensed (LTE-U) radio access technology, or NR technology in anunlicensed band such as the 5 GHz industrial, scientific, and medical(ISM) band. When operating in unlicensed radio frequency spectrum bands,devices such as the base stations 105 and the UEs 115 may employ carriersensing for collision detection and avoidance. In some examples,operations in unlicensed bands may be based on a carrier aggregationconfiguration in conjunction with component carriers operating in alicensed band (e.g., LAA). Operations in unlicensed spectrum may includedownlink transmissions, uplink transmissions, P2P transmissions, or D2Dtransmissions, among other examples.

A base station 105 or a UE 115 may be equipped with multiple antennas,which may be used to employ techniques such as transmit diversity,receive diversity, multiple-input multiple-output (MIMO) communications,or beamforming. The antennas of a base station 105 or a UE 115 may belocated within one or more antenna arrays or antenna panels, which maysupport MIMO operations or transmit or receive beamforming. For example,one or more base station antennas or antenna arrays may be co-located atan antenna assembly, such as an antenna tower. In some examples,antennas or antenna arrays associated with a base station 105 may belocated in diverse geographic locations. A base station 105 may have anantenna array with a number of rows and columns of antenna ports thatthe base station 105 may use to support beamforming of communicationswith a UE 115. Likewise, a UE 115 may have one or more antenna arraysthat may support various MIMO or beamforming operations. Additionally oralternatively, an antenna panel may support radio frequency beamformingfor a signal transmitted via an antenna port.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105, a UE 115) to shape or steeran antenna beam (e.g., a transmit beam, a receive beam) along a spatialpath between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that some signals propagatingat particular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying amplitude offsets, phase offsets, or both to signals carriedvia the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

The wireless communications system 100 may be a packet-based networkthat operates according to a layered protocol stack. In the user plane,communications at the bearer or Packet Data Convergence Protocol (PDCP)layer may be IP-based. An RLC layer may perform packet segmentation andreassembly to communicate over logical channels. A MAC layer may performpriority handling and multiplexing of logical channels into transportchannels. The MAC layer may also use error detection techniques, errorcorrection techniques, or both to support retransmissions at the MAClayer to improve link efficiency. In the control plane, the RadioResource Control (RRC) protocol layer may provide establishment,configuration, and maintenance of an RRC connection between a UE 115 anda base station 105 or a core network 130 supporting radio bearers foruser plane data. At the physical layer, transport channels may be mappedto physical channels.

The UEs 115 and the base stations 105 may support retransmissions ofdata to increase the likelihood that data is received successfully.Hybrid automatic repeat request (HARQ) feedback is one technique forincreasing the likelihood that data is received correctly over acommunication link 125. HARQ may include a combination of errordetection (e.g., using a cyclic redundancy check (CRC)), forward errorcorrection (FEC), and retransmission (e.g., automatic repeat request(ARQ)). HARQ may improve throughput at the MAC layer in poor radioconditions (e.g., low signal-to-noise conditions). In some examples, adevice may support same-slot HARQ feedback, where the device may provideHARQ feedback in a specific slot for data received in a previous symbolin the slot. In other cases, the device may provide HARQ feedback in asubsequent slot, or according to some other time interval.

A base station 105 may transmit a set of network coding encoded packetswith an associated redundancy overhead. That is, a portion of the set ofnetwork coding encoded packets may include redundant data. In somecases, this may enable a receiving UE 115 to decode the set of networkcoding encoded packets even in cases of one or more missing packets. Insome wireless communications systems 100, the base station 105 may be incommunication with multiple UEs 115 and may utilize a same redundancyoverhead for unicast transmissions to each of the UEs 115. However, aquantity of redundant network coding encoded packets (e.g., a redundancyoverhead) necessary to achieve reliable communications with a UE 115 maybe based on a channel quality associated with that UE 115. Therefore,utilizing a same redundancy overhead for unicast transmissions to UEs115 that may not have similar channel qualities may result in excessiveredundancy overhead or insufficient redundancy overhead fortransmissions with some UEs 115.

In the example of wireless communications system 100, a base station 105may use a dynamic redundancy overhead for unicast transmissions todifferent UEs 115. This may enable the base station 105 to decreaseunnecessary overhead for transmissions with UEs 115 associated withhigher channel qualities while still maintaining reliable communicationswith UEs 115 associated with lower channel qualities. For example, thebase station 105 may determine a failure rate associated with atransmission to each UE 115 and the base station 105 may identify aredundancy overhead for transmissions with each UE 115 based on theidentified failure rate. The redundancy overhead updates may be basestation-initiated or UE-initiated (e.g., the base station 105 may updatethe redundancy overhead based on receiving a request for the updatedredundancy overhead from the UE 115). In one case, the redundancyoverhead updates may be based on a periodicity for redundancy overheadupdates. In another case, the redundancy overhead updates may be basedon the identified failure rate. That is, the base station 105 may updatethe redundancy overhead in cases that the identified failure rateexceeds a threshold failure rate.

FIG. 2 illustrates an example of a wireless communications system 200that supports network coding with dynamic redundancy overhead inaccordance with aspects of the present disclosure. In some examples, thewireless communications system 200 may implement aspects of wirelesscommunications system 100. The wireless communications system 200 mayinclude UEs 115-a, 115-b, and 115-c and a base station 105-a, which maybe examples of a UE 115 and a base station 105, respectively, asdescribed with reference to FIG. 1.

The base station 105-a may be in communication with multiple UEs 115including UE 115-a, UE 115-b, and UE 115-c. That is, the base station105-a may be in communication with the UE 115-a via the channel 205-a,the UE 115-b via the channel 205-b, and the UE 115-c via the channel205-c. The base station 105-a may use the channels 205 to transmit setsof network coding encoded packets 210 to the UEs 115. For example, thebase station 105-a may transmit a unicast transmission including the setof packets 210-a to the UE 115-a via the channel 205-a. Additionally,the base station 105-a may transmit a different unicast transmissionincluding the set of packets 210-b to the UE 115-b via the channel205-b.

Each of the sets of packets 210 may be associated with a redundancyoverhead. That is, each set of packets 210 may include one or moreencoded packets 215 and one or more redundant packets 220. The one ormore redundant packets 220 may enable the UE 115 to receive less thanall of the packets within the set of packets 210 and still successfullyreceive the data within the set of packets 210. That is, a UE 115 mayrely on one or more redundant packets 220 to recover one or more missingpackets. In some instances, sets of packets 210 with a higher redundancyoverhead (e.g., more redundant packets 220) may enable a UE 115 torecover more missing packets than sets of packets 210 with a lowerredundancy overhead.

The base station 105-a may dynamically identify a redundancy overheadfor the sets of packets 210 based on a quality of the channel 205 forcommunications with the UE 115. For example, if the base station 105-adetermines that a channel 205 is associated with a relatively highchannel quality, the base station 105-a may utilize a relatively lowredundancy overhead (e.g., by including less redundant packets 220within the set of packets 210). Additionally, if the base station 105-adetermines that a channel 205 is associated with a relatively lowchannel quality, the base station 105-a may utilize a relatively highredundancy overhead (e.g., by including more redundant packets 220within the set of packets 210).

In the example of wireless communications system 200, the base station105-a may utilize a relatively low redundancy overhead for transmittingthe set of packets 210-a to the UE 115-a via the channel 205-a (e.g.,when compared to the redundancy overheads the base station 105-a usesfor transmissions to the other UEs 115). That is, the base station 105-amay determine that the channel quality of the channel 205-a isrelatively high, and may therefore determine to transmit less redundantpackets 220-a within the set of packets 210-a (e.g., and more encodedpackets 215-a). Additionally, the base station 105-a may utilize arelatively high redundancy overhead for transmitting the set of packets210-b to the UE 115-b via the channel 205-b. That is, the base station105-a may determine that the channel quality of channel 205-b isrelatively low (e.g., when compared to the channels 205-a and 205-c),and may therefore determine to transmit more redundant packets 220-bwithin the set of packets 210-b (and less encoded packets 215-b).

The base station 105-a may determine the channel quality of the channels205 based on a failure rate associated with transmitting sets of packets210 to the UE 115 via the channel 205. A failure rate associated withtransmitting a set of packets 210 may be based on a quantity of theencoded packets 215 the UE 115 is unable to receive when monitoring thechannel 205 for the set of packets 210. For example, the base station105-a may transmit the set of packets 210-c to the UE 115-c and thefailure rate associated with that transmission may be based on thenumber of packets within the set of packets 210 that the UE 115-c isunable to receive.

The base station 105-a may determine the failure rate based on a messagereceived from the UE 115 (e.g., via a MAC-control element (CE), viauplink control information (UCI)). For example, a UE 115 may transmit afeedback message (e.g., a HARQ NACK message) in response to receiving aset of packets 210 and the base station 105-a may determine the failurerate based on receiving the feedback message. That is, the feedbackmessage may indicate one or more packets within the set of packets 210that the UE 115 was unable to receive and the base station 105-a maydetermine the failure rate based on that indication. In another example,a UE 115 may transmit a retransmission request (e.g., a radio linkcontrol (RLC) status report message) for one or more of packets within aset of packets 210 and the base station 105-a may determine the failurerate based on the retransmission request. In another example, the UE 115may transmit a message indicating the failure rate itself. For example,the UE 115 may determine the failure rate and transmit a message to thebase station 105-a indicating the determined failure rate.

The base station 105-a may identify a redundancy overhead fortransmissions of sets of packets 210 based on the failure rateassociated with a previously-transmitted set of packets 210. That is,the base station 105-a may transmit a first set of packets 210 to the UE115 using a first redundancy overhead and may identify a secondredundancy overhead for future transmissions of second sets of packets210 that is based on a failure rate associated with the transmission ofthe first set of packets 210. Equation 1, shown below, illustrates anexample equation that the base station 105-a may utilize to identify aredundancy overhead R to use for transmissions based on a determinedfailure rate, E.

$\begin{matrix}{R = {{\frac{1}{1 - E} - 1} = \frac{E}{1 - E}}} & (1)\end{matrix}$

Equation 2, shown below, illustrates another example equation that thebase station 105-a may utilize to identify a redundancy overhead R touse for transmissions based on a determined failure rate, E.

$\begin{matrix}{R = \frac{d - 1 + E}{1 - E}} & (2)\end{matrix}$

In the Example of Equation 2, d may be defined according to Equation 3,shown below, where k is a quantity of sub-packets that an originalpacket is divided into (e.g., prior to network coding). In the exampleof Equation 2, d may be greater than 1 and the higher d is, the greatera likelihood that a UE may decode the transmission to successfullyrecover the original packet.

$\begin{matrix}{d = {1 + \frac{1}{k}}} & (3)\end{matrix}$

In some examples, the base station 105-a may identify redundancyoverheads for future transmissions of sets of packets 210 according to aperiodicity (e.g., every ‘T’ slots). In another example, the basestation 105-a may identify redundancy overheads for future transmissionsof sets of packets 210 when a failure rate of a transmission of a set ofpackets 210 exceeds a threshold failure rate. Additionally, the basestation 105-a may identify redundancy overheads for future transmissionsof sets of packets 210 in response to a request for an updatedredundancy overhead from a UE 115.

When the base station 105-a identifies a redundancy overhead fortransmitting a set of packets 210 to a UE 115, the base station 105-amay use network coding to encode the set of packets 210 according to theidentified redundancy overhead. Thus, the base station 105-a maygenerate a set of packets 210 include encoded packets 215 and one ormore redundant packets 220. The base station 105-a may then transmit oneor more sets of packets 210 to the UE 115 using the identifiedredundancy overhead.

FIG. 3 illustrates an example of a process flow 300 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. For example, the UE 115-d may be anexample of the UEs 115 as described with respect to FIGS. 1 and 2.Additionally, the base station 105-b may be an example of the basestations 105 as described with respect to FIGS. 1 and 2. In the processflow 300, the base station 105-b may update a redundancy overhead fortransmitting sets of network coding encoded packets to the UE 115-dbased on receiving a request from the UE 115-d to update the redundancyoverhead.

At 305, the base station 105-b may transmit an RRC message to the UE115-d. In some examples, the RRC message may indicate a configurationfor updating the redundancy overhead for transmitting sets of networkcoding encoded packets. For example, the RRC message may indicate aperiodicity for updating redundancy overheads or a threshold failurerate associated with updating redundancy overheads.

At 310, the base station 105-b may transmit, to the UE 115-d, a firstset of network coding encoded packets including a first redundancyoverhead. Additionally, the UE 115-d may attempt to receive the firstset of network coding encoded packets based on the base station 105-btransmitting the set of network coding encoded packets.

At 315, the UE 115-d may optionally determine a failure rate associatedwith the set of network coding encoded packets received from the basestation 105-b at 310. For example, the UE 115-d may estimate the failurerate based on the quantity of the first set of network coding encodedpackets that are successfully received when attempting to receive eachof the first set of network coding encoded packets. In another example,the UE 115-d may estimate the failure rate based on identifying aquantity of the first set of network coding encoded packets that arereceived via an RLC entity at the UE 115-d. That is, the UE 115-d mayidentify one or more empty RLC packet numbers (e.g., indicating that oneor more of the first set of network coding encoded packets are notreceived via the RLC entity). Here, the UE 115-d may estimate thefailure rate based on the quantity of the first set of network codingencoded packets that are received via the RLC entity.

At 320, the UE 115-d may transmit, to the base station 105-b, a requestfor an updated redundancy overhead for one or more second sets ofnetwork coding encoded packets. For example, the UE 115-d may transmitthe request based on the configuration (e.g., indicated by the RRCmessage) for updating the redundancy overhead for transmitting sets ofnetwork coding encoded packets. That is, the UE 115-d may determine thatthe failure rate identified at 320 exceeds a threshold failure rate. Inanother case, the UE 115-d may transmit the request for the updatedredundancy overhead according to the configured periodicity. The UE115-d may transmit the request using a MAC-CE or UCI. In some instances,the UE 115-d may additionally include the determined failure rate in therequest. Additionally, the request may indicate the updated redundancyoverhead for the one or more second sets of network coding encodedpackets.

At 325, the base station 105-b may determine the failure rate associatedwith the set of network coding encoded packets received from the basestation 105-b at 310. For example, the base station 105-b may determinethe failure rate based on receiving an indication of the failure ratewithin the updated redundancy overhead request received at 320. Inanother example, the base station 105-b may determine the failure ratebased on receiving a feedback message or retransmission request from theUE 115-d. Additionally, the base station 105-b may determine the failurerate based on a combination of receiving a feedback message orretransmission request from the UE 115-d and receiving the indication ofthe failure rate from the UE 115-d.

At 330, the base station 105-b may identify a redundancy associated withone or more second sets of network coding encoded packets (e.g., basedon the determined failure rate). In some cases, the base station 105-bmay identify the redundancy overhead for the one or more second sets ofnetwork coding encoded packets based on receiving the request to updatethe redundancy overhead from the UE 115-d at 320.

At 335, the base station 105-b may transmit, to the UE 115-d, one ormore second sets of network coding encoded packets having the identifiedredundancy overhead. That is, the base station 105-b may encode the oneor more second sets of packets using network coding and according to theidentified redundancy overhead. The base station 105-b may then transmitthe one or more second sets of network coding encoded packets to the UE115-d.

FIG. 4 illustrates an example of a process flow 400 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. For example, the UE 115-e may be anexample of the UEs 115 as described with respect to FIGS. 1 through 3.Additionally, the base station 105-d may be an example of the basestations 105 as described with respect to FIGS. 1 through 3. In theprocess flow 400, the base station 105-c may determine to update aredundancy overhead for transmitting sets of network coding encodedpackets to the UE 115-e based on a redundancy overhead updateperiodicity or an identified failure rate exceeding a threshold.

At 405, the base station 105-b may transmit an RRC message to the UE115-e. In some examples, the RRC message may indicate a configurationfor updating the redundancy overhead for transmitting sets of networkcoding encoded packets. For example, the RRC message may indicate aperiodicity for updating redundancy overheads or a threshold failurerate associated with updating redundancy overheads.

At 410, the base station 105-c may transmit, to the UE 115-e, a firstset of network coding encoded packets including a first redundancyoverhead. Additionally, the UE 115-e may attempt to receive the firstset of network coding encoded packets based on the base station 105-ctransmitting the set of network coding encoded packets.

At 415, the UE 115-e may optionally determine a failure rate associatedwith the set of network coding encoded packets received from the basestation 105-c at 410. For example, the UE 115-e may estimate the failurerate based on the quantity of the first set of network coding encodedpackets that are successfully received when attempting to receive eachof the first set of network coding encoded packets. In another example,the UE 115-e may estimate the failure rate based on identifying aquantity of the first set of network coding encoded packets that arereceived via an RLC entity at the UE 115-e. That is, the UE 115-e mayidentify one or more empty RLC packet numbers (e.g., indicating that oneor more of the first set of network coding encoded packets are notreceived via the RLC entity). Here, the UE 115-e may estimate thefailure rate based on the quantity of the first set of network codingencoded packets that are received via the RLC entity.

At 420, the UE 115-e may transmit a message to the base station 105-c.For example, the message may be a feedback message (e.g., a HARQ NACKmessage) to the base station 105-c. In some cases, the feedback messagemay indicate a quantity of the first set of network coding encodedpackets that the UE 115-e did not successfully receive. In anotherexample, the message may be a retransmission request (e.g., an RLCstatus report message). Additionally, the first message may include anindication of the failure rate (e.g., determined by the UE 115-e at415). In some cases, the UE 115-e may transmit the message via a MAC-CEor UCI.

At 425, the base station 105-c may determine the failure rate associatedwith the first set of network coding encoded packets. For example, thebase station 105-c may determine the failure rate based on receiving themessage from the UE 115-e at 420.

At 430, the base station 105-c identify a redundancy associated with oneor more second sets of network coding encoded packets (e.g., based onthe determined failure rate). For example, the base station 105-c mayidentify the redundancy overhead based on the configuration (e.g.,indicated by the RRC message) for updating the redundancy overhead forsets of network coding encoded packets. That is, the base station 105-cmay identify the redundancy overhead based on determining that thefailure rate determined at 425 exceeds a threshold failure rate. Inanother case, the base station 105-c may identify the redundancyoverhead according to the configured periodicity.

At 435, the base station 105-c may transmit, to the UE 115-e, one ormore second sets of network coding encoded packets having the identifiedredundancy overhead. That is, the base station 105-c may encode the oneor more second sets of packets using network coding and according to theidentified redundancy overhead. The base station 105-c may then transmitthe one or more second sets of network coding encoded packets to the UE115-e.

FIG. 5 illustrates an example of protocol stack functions 500 thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure. In some examples, protocol stackfunctions 500 may implement aspects of wireless communications systems100 or 200. In this example, a protocol stack at a wireless device(e.g., a UE or base station as described herein) may include a PDCPlayer 505 that provides PDCP PDUs to the RLC layer 510. The RLC layer510 may include a network coding sub-layer 520, and provide networkcoded RLC PDUs to MAC layer 545. The MAC layer 545 may interact with thephysical (PHY) layer 555 to provide communications over channel(s) 565.Such protocol stack functions 500 may be performed at any device thattransmits network coding encoded packets as discussed herein, such as aUE, base station, and the like. A receiving device may includecorresponding layers that perform corresponding receive and decodingfunctions.

PDCP layer 505 which may provide header compression of IP packets,integrity protection, and ciphering, and may provide PDCP PDUs to theRLC layer 510. The RLC layer 510 may perform packet segmentation andreassembly to communicate over logical channels. The MAC layer 545 mayperform priority handling and multiplexing of logical channels intotransport channels. The MAC layer 545 may also use error detectiontechniques, error correction techniques, or both to supportretransmissions at the MAC layer 545 to improve link efficiency. At thePHY layer 555, transport channels may be mapped to physical channels.

In the example of FIG. 5, a transmitting device may generate an RLC SDUfrom one or more PDCP PDUs. In some aspects, a single PDCP PDU may beincluded in an RLC SDU. In some aspects, optionally, multiple PDCP PDUsmay be included in an RLC SDU, such as by concatenating multiple PDCPPDUs at PDCP PDU concatenation function 515. In some aspects, thetransmitting device may determine whether to include a single PDCP PDUin a single RLC SDU or whether to concatenate multiple PDCP PDUs in asingle RLC SDU based at least in part on a size of the PDCP PDU. Forexample, if the size of the PDCP PDU satisfies a threshold (e.g., isgreater than or equal to the threshold), then the transmitting devicemay include only the PDCP PDU (e.g., a single PDCP PDU) in a single RLCSDU. If the size of the PDCP PDU does not satisfy a threshold (e.g., isless than or equal to the threshold), then the encoder may concatenatemultiple PDCP PDUs (e.g., a set of PDCP PDUs with a total size that isless than or equal to the threshold) into a single RLC SDU.

At 525, the RLC layer 510 may divide the RLC SDU into a number of datablocks. For example, the RLC layer 510 may divide the RLC SDU into kdata blocks, shown as s₁, through s_(K). In some aspects, the number ofdata blocks (e.g., the value of k) is indicated in a configurationmessage (e.g., an RRC message), which may provide configurationinformation to network coding. Additionally or alternatively, thetransmitting device may determine the number of data blocks based atleast in part on an RLC header size (e.g., an RLC header size fornetwork coding encoding packets), a packet payload size, an overheadbudget, a channel condition, a target error probability, or anycombinations thereof. The data blocks may be provided to network codingsub-layer 520.

At 530, the network coding sub-layer 520 may encode the data blocks intoa number of RLC packets (e.g., a set of network coding encoded packets)using network coding. For example, the network coding sub-layer 520 mayencode k data blocks into N RLC packets, shown as p₁, through p_(N),using network coding techniques (e.g., Raptor codes). In some aspects,the number of network coding encoded packets (e.g., the value of N) isindicated in a configuration message (e.g., an RRC message) thatconfigures network coding. Additionally or alternatively, thetransmitting device may determine the number of network coding encodedpackets based at least in part on a target error probability, a channelcondition, payload size, or any combinations thereof.

The network coding sub-layer 520 may encode the data blocks into the setof network coding encoding packets having a certain redundancy overhead.That is, one or more of the set of network coding encoding packets maybe redundant. The redundancy overhead R associated with the set ofnetwork coding encoding packets may be defined below, according toEquation 4. Here, N may correspond to the quantity of the network codingencoding packets within the set of network coding encoding packets and kmay correspond to the quantity of data blocks.

$\begin{matrix}{R = \frac{N - k}{k}} & (4)\end{matrix}$

In some cases, the network coding sub-layer 520 may dynamically identifya redundancy overhead for encoding the data blocks into the set ofnetwork coding encoded packets based on a failure rate associated with apreviously transmitted set of network coding encoded packets. Thus, theset of network coding encoded packets may include a quantity ofredundant packets that is based on the determined failure rate. Thenetwork coding sub-layer 520 may encode the data blocks into the numberof RLC packets (e.g., the set of network coding encoded packets)according to the identified redundancy overhead.

At 540, the RLC layer 510 may map the network coding encoded packetsfrom the network coding sub-layer 520 to a corresponding number of RLCPDUs. For example, the RLC layer 510 may map N network coding encodedpackets to N RLC PDUs, shown as PDUi, through PDUN. In some aspects, thenumber of RLC PDUs (e.g., the value of N) may be indicated in aconfiguration message (e.g., an RRC message) that configured networkcoding. Additionally or alternatively, the transmitting device maydetermine the number of RLC PDUs based at least in part on a targeterror probability, a channel condition, payload size, or anycombinations thereof.

At 550, the RLC layer 510 may include the RLC PDUs in a MAC PDU that isprovided to MAC layer 545. The MAC layer 545 may perform priorityhandling and multiplexing the MAC PDU and logical channels intotransport channels, and provide the transport channels to the PHY layer555. The transmitting device may transmit the RLC PDUs (e.g., in the MACPDU) to a decoder or a receiving device, such as a UE or a base station.In some aspects, the transmitting may transmit using transmit diversity,such as by transmitting on multiple carriers (e.g., using frequencydiversity), transmitting using multiple beams (e.g., using spatialdiversity), and the like. For example, the transmitting device maytransmit a first transmission 570-a containing M RLC PDUs via a firstcarrier 560-a (where M<N) and/or a first beam, and may transmit a secondtransmission 570-b containing (N−M) RLC PDUs via a second carrier 560-band/or a second beam. The receiving device may receive the transmissions570, and use network coding techniques to decode the RLC PDUs.

FIG. 6 shows a block diagram 600 of a device 605 that supports networkcoding with dynamic redundancy overhead in accordance with aspects ofthe present disclosure. The device 605 may be an example of aspects of abase station 105 as described herein. The device 605 may include areceiver 610, a transmitter 615, and a communications manager 620. Thedevice 605 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

The receiver 610 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to network coding withdynamic redundancy overhead). Information may be passed on to othercomponents of the device 605. The receiver 610 may utilize a singleantenna or a set of multiple antennas.

The transmitter 615 may provide a means for transmitting signalsgenerated by other components of the device 605. For example, thetransmitter 615 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to network coding with dynamic redundancy overhead). Insome examples, the transmitter 615 may be co-located with a receiver 610in a transceiver module. The transmitter 615 may utilize a singleantenna or a set of multiple antennas.

The communications manager 620, the receiver 610, the transmitter 615,or various combinations thereof or various components thereof may beexamples of means for performing various aspects of network coding withdynamic redundancy overhead as described herein. For example, thecommunications manager 620, the receiver 610, the transmitter 615, orvarious combinations or components thereof may support a method forperforming one or more of the functions described herein.

In some examples, the communications manager 620, the receiver 610, thetransmitter 615, or various combinations or components thereof may beimplemented in hardware (e.g., in communications management circuitry).The hardware may include a processor, a DSP, an ASIC, afield-programmable gate array (FPGA) or other programmable logic device,a discrete gate or transistor logic, discrete hardware components, orany combination thereof configured as or otherwise supporting a meansfor performing the functions described in the present disclosure. Insome examples, a processor and memory coupled with the processor may beconfigured to perform one or more of the functions described herein(e.g., by executing, by the processor, instructions stored in thememory).

Additionally or alternatively, in some examples, the communicationsmanager 620, the receiver 610, the transmitter 615, or variouscombinations or components thereof may be implemented in code (e.g., ascommunications management software or firmware) executed by a processor.If implemented in code executed by a processor, the functions of thecommunications manager 620, the receiver 610, the transmitter 615, orvarious combinations or components thereof may be performed by ageneral-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or anycombination of these or other programmable logic devices (e.g.,configured as or otherwise supporting a means for performing thefunctions described in the present disclosure).

In some examples, the communications manager 620 may be configured toperform various operations (e.g., receiving, monitoring, transmitting)using or otherwise in cooperation with the receiver 610, the transmitter615, or both. For example, the communications manager 620 may receiveinformation from the receiver 610, send information to the transmitter615, or be integrated in combination with the receiver 610, thetransmitter 615, or both to receive information, transmit information,or perform various other operations as described herein.

The communications manager 620 may support wireless communication at abase station in accordance with examples as disclosed herein. Forexample, the communications manager 620 may be configured as orotherwise support a means for determining a failure rate associated witha transmission of a first set of network coding encoded packets to a UE.The communications manager 620 may be configured as or otherwise supporta means for identifying a redundancy overhead associated with one ormore second sets of network coding encoded packets for the UE based onthe failure rate associated with the transmission of the first set ofnetwork coding encoded packets to the UE. The communications manager 620may be configured as or otherwise support a means for transmitting theone or more second sets of network coding encoded packets to the UE, theone or more second sets of network coding encoded packets beingtransmitted using the identified redundancy overhead.

By including or configuring the communications manager 620 in accordancewith examples as described herein, the device 605 (e.g., a processorcontrolling or otherwise coupled to the receiver 610, the transmitter615, the communications manager 620, or a combination thereof) maysupport techniques for more efficient utilization of communicationresources while still maintaining reliable communications. That is, thecommunications manager 620 may be configured to dynamically allocateresources for redundancy overhead based on a channel quality, which maydecrease a likelihood of excessive redundancy overhead (e.g., resultingin less efficient utilization of communication resources) andinsufficient redundancy overhead (e.g., resulting in less reliablecommunications).

FIG. 7 shows a block diagram 700 of a device 705 that supports networkcoding with dynamic redundancy overhead in accordance with aspects ofthe present disclosure. The device 705 may be an example of aspects of adevice 605 or a base station 105 as described herein. The device 705 mayinclude a receiver 710, a transmitter 715, and a communications manager720. The device 705 may also include a processor. Each of thesecomponents may be in communication with one another (e.g., via one ormore buses).

The receiver 710 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to network coding withdynamic redundancy overhead). Information may be passed on to othercomponents of the device 705. The receiver 710 may utilize a singleantenna or a set of multiple antennas.

The transmitter 715 may provide a means for transmitting signalsgenerated by other components of the device 705. For example, thetransmitter 715 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to network coding with dynamic redundancy overhead). Insome examples, the transmitter 715 may be co-located with a receiver 710in a transceiver module. The transmitter 715 may utilize a singleantenna or a set of multiple antennas.

The device 705, or various components thereof, may be an example ofmeans for performing various aspects of network coding with dynamicredundancy overhead as described herein. For example, the communicationsmanager 720 may include a failure rate manager 725, a redundancyoverhead manager 730, a packet transmitter 735, or any combinationthereof. The communications manager 720 may be an example of aspects ofa communications manager 620 as described herein. In some examples, thecommunications manager 720, or various components thereof, may beconfigured to perform various operations (e.g., receiving, monitoring,transmitting) using or otherwise in cooperation with the receiver 710,the transmitter 715, or both. For example, the communications manager720 may receive information from the receiver 710, send information tothe transmitter 715, or be integrated in combination with the receiver710, the transmitter 715, or both to receive information, transmitinformation, or perform various other operations as described herein.

The communications manager 720 may support wireless communication at abase station in accordance with examples as disclosed herein. Thefailure rate manager 725 may be configured as or otherwise support ameans for determining a failure rate associated with a transmission of afirst set of network coding encoded packets to a UE. The redundancyoverhead manager 730 may be configured as or otherwise support a meansfor identifying a redundancy overhead associated with one or more secondsets of network coding encoded packets for the UE based on the failurerate associated with the transmission of the first set of network codingencoded packets to the UE. The packet transmitter 735 may be configuredas or otherwise support a means for transmitting the one or more secondsets of network coding encoded packets to the UE, the one or more secondsets of network coding encoded packets being transmitted using theidentified redundancy overhead.

FIG. 8 shows a block diagram 800 of a communications manager 820 thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure. The communications manager 820may be an example of aspects of a communications manager 620, acommunications manager 720, or both, as described herein. Thecommunications manager 820, or various components thereof, may be anexample of means for performing various aspects of network coding withdynamic redundancy overhead as described herein. For example, thecommunications manager 820 may include a failure rate manager 825, aredundancy overhead manager 830, a packet transmitter 835, a UE messagereceiver 840, a control message transmitter 845, or any combinationthereof. Each of these components may communicate, directly orindirectly, with one another (e.g., via one or more buses).

The communications manager 820 may support wireless communication at abase station in accordance with examples as disclosed herein. Thefailure rate manager 825 may be configured as or otherwise support ameans for determining a failure rate associated with a transmission of afirst set of network coding encoded packets to a UE. The redundancyoverhead manager 830 may be configured as or otherwise support a meansfor identifying a redundancy overhead associated with one or more secondsets of network coding encoded packets for the UE based on the failurerate associated with the transmission of the first set of network codingencoded packets to the UE. The packet transmitter 835 may be configuredas or otherwise support a means for transmitting the one or more secondsets of network coding encoded packets to the UE, the one or more secondsets of network coding encoded packets being transmitted using theidentified redundancy overhead.

In some examples, to support identifying the redundancy overhead, theredundancy overhead manager 830 may be configured as or otherwisesupport a means for identifying that the failure rate associated withthe transmission of the first set of network coding encoded packets tothe UE exceeds a threshold failure rate. In some examples, to supportidentifying the redundancy overhead, the redundancy overhead manager 830may be configured as or otherwise support a means for determining theredundancy overhead based on the failure rate exceeding the thresholdfailure rate. In some cases, to support identifying the redundancyoverhead, the redundancy overhead manager 830 may be configured as orotherwise support a means for identifying the redundancy overheadperiodically and in accordance with a periodicity for identifyingredundancy overheads. In some instances, to support identifying theredundancy overhead, the redundancy overhead manager 830 may beconfigured as or otherwise support a means for identifying theredundancy overhead in response to a first message, received from theUE, requesting an updated redundancy overhead for the one or more secondsets of network coding encoded packets.

In some examples, the control message transmitter 845 may be configuredas or otherwise support a means for transmitting, to the UE, a radioresource control message indicating one or more of a periodicity forupdating redundancy overheads and a threshold failure rate associatedwith updating redundancy overheads, where the first message is inaccordance with the radio resource control message.

In some examples, the UE message receiver 840 may be configured as orotherwise support a means for receiving, in the first message, anindication of the failure rate, where determining the failure rateassociated with the transmission of the first set of network codingencoded packets to the UE is based on the indication of the failurerate. In some cases, the UE message receiver 840 may be configured as orotherwise support a means for receiving the first message via a MAC-CEor UCI. In some examples, the UE message receiver 840 may be configuredas or otherwise support a means for receiving a first message from theUE in response to the transmission of the first set of network codingencoded packets to the UE, where determining the failure rate is basedon the first message. In some examples, the first message is a feedbackmessage or a retransmission request associated with the transmission ofthe first set of network coding encoded packets. In some instances, thefeedback message is a HARQ NACK feedback message. In some examples,determining the failure rate includes estimating the failure rate basedon the feedback message or the retransmission request. In some cases,the retransmission request is an RLC status report message. In someexamples, the first message includes an indication of the failure rate.Here, the determined failure rate is the indicated failure rate.

In some examples, the packet transmitter 835 may be configured as orotherwise support a means for transmitting the first set of networkcoding encoded packets to the UE including an initial redundancyoverhead different from the identified redundancy overhead, wheredetermining the failure rate is based on transmitting the first set ofnetwork coding encoded packets to the UE. In some cases, the packettransmitter 835 may be configured as or otherwise support a means fortransmitting a third set of network coding encoded packets to a secondUE different from the UE, where the third set of network coding encodedpackets includes a second redundancy overhead different from theidentified redundancy overhead.

FIG. 9 shows a diagram of a system 900 including a device 905 thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure. The device 905 may be an exampleof or include the components of a device 605, a device 705, or a basestation 105 as described herein. The device 905 may communicatewirelessly with one or more base stations 105, UEs 115, or anycombination thereof. The device 905 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, such as a communicationsmanager 920, a network communications manager 910, a transceiver 915, anantenna 925, a memory 930, code 935, a processor 940, and aninter-station communications manager 945. These components may be inelectronic communication or otherwise coupled (e.g., operatively,communicatively, functionally, electronically, electrically) via one ormore buses (e.g., a bus 950).

The network communications manager 910 may manage communications with acore network 130 (e.g., via one or more wired backhaul links). Forexample, the network communications manager 910 may manage the transferof data communications for client devices, such as one or more UEs 115.

In some cases, the device 905 may include a single antenna 925. However,in some other cases the device 905 may have more than one antenna 925,which may be capable of concurrently transmitting or receiving multiplewireless transmissions. The transceiver 915 may communicatebi-directionally, via the one or more antennas 925, wired, or wirelesslinks as described herein. For example, the transceiver 915 mayrepresent a wireless transceiver and may communicate bi-directionallywith another wireless transceiver. The transceiver 915 may also includea modem to modulate the packets, to provide the modulated packets to oneor more antennas 925 for transmission, and to demodulate packetsreceived from the one or more antennas 925. The transceiver 915, or thetransceiver 915 and one or more antennas 925, may be an example of atransmitter 615, a transmitter 715, a receiver 610, a receiver 710, orany combination thereof or component thereof, as described herein.

The memory 930 may include random access memory (RAM) and read-onlymemory (ROM). The memory 930 may store computer-readable,computer-executable code 935 including instructions that, when executedby the processor 940, cause the device 905 to perform various functionsdescribed herein. The code 935 may be stored in a non-transitorycomputer-readable medium such as system memory or another type ofmemory. In some cases, the code 935 may not be directly executable bythe processor 940 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein. In some cases, thememory 930 may contain, among other things, a basic I/O system (BIOS)which may control basic hardware or software operation such as theinteraction with peripheral components or devices.

The processor 940 may include an intelligent hardware device (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 940 may be configured to operate a memoryarray using a memory controller. In some other cases, a memorycontroller may be integrated into the processor 940. The processor 940may be configured to execute computer-readable instructions stored in amemory (e.g., the memory 930) to cause the device 905 to perform variousfunctions (e.g., functions or tasks supporting network coding withdynamic redundancy overhead). For example, the device 905 or a componentof the device 905 may include a processor 940 and memory 930 coupled tothe processor 940, the processor 940 and memory 930 configured toperform various functions described herein.

The inter-station communications manager 945 may manage communicationswith other base stations 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager945 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager945 may provide an X2 interface within an LTE/LTE-A wirelesscommunications network technology to provide communication between basestations 105.

The communications manager 920 may support wireless communication at abase station in accordance with examples as disclosed herein. Forexample, the communications manager 920 may be configured as orotherwise support a means for determining a failure rate associated witha transmission of a first set of network coding encoded packets to a UE.The communications manager 920 may be configured as or otherwise supporta means for identifying a redundancy overhead associated with one ormore second sets of network coding encoded packets for the UE based onthe failure rate associated with the transmission of the first set ofnetwork coding encoded packets to the UE. The communications manager 920may be configured as or otherwise support a means for transmitting theone or more second sets of network coding encoded packets to the UE, theone or more second sets of network coding encoded packets beingtransmitted using the identified redundancy overhead.

By including or configuring the communications manager 920 in accordancewith examples as described herein, the device 905 may support techniquesfor improved communication reliability and more efficient utilization ofcommunication resources. That is, the communications manager 920 may beconfigured to dynamically identify redundancy overhead based on achannel quality, which may decrease a likelihood of excessive redundancyoverhead (e.g., resulting in less efficient utilization of communicationresources) and insufficient redundancy overhead (e.g., resulting in lessreliable communications).

In some examples, the communications manager 920 may be configured toperform various operations (e.g., receiving, monitoring, transmitting)using or otherwise in cooperation with the transceiver 915, the one ormore antennas 925, or any combination thereof. Although thecommunications manager 920 is illustrated as a separate component, insome examples, one or more functions described with reference to thecommunications manager 920 may be supported by or performed by theprocessor 940, the memory 930, the code 935, or any combination thereof.For example, the code 935 may include instructions executable by theprocessor 940 to cause the device 905 to perform various aspects ofnetwork coding with dynamic redundancy overhead as described herein, orthe processor 940 and the memory 930 may be otherwise configured toperform or support such operations.

FIG. 10 shows a block diagram 1000 of a device 1005 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The device 1005 may be an example ofaspects of a UE 115 as described herein. The device 1005 may include areceiver 1010, a transmitter 1015, and a communications manager 1020.The device 1005 may also include a processor. Each of these componentsmay be in communication with one another (e.g., via one or more buses).

The receiver 1010 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to network coding withdynamic redundancy overhead). Information may be passed on to othercomponents of the device 1005. The receiver 1010 may utilize a singleantenna or a set of multiple antennas.

The transmitter 1015 may provide a means for transmitting signalsgenerated by other components of the device 1005. For example, thetransmitter 1015 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to network coding with dynamic redundancy overhead). Insome examples, the transmitter 1015 may be co-located with a receiver1010 in a transceiver module. The transmitter 1015 may utilize a singleantenna or a set of multiple antennas.

The communications manager 1020, the receiver 1010, the transmitter1015, or various combinations thereof or various components thereof maybe examples of means for performing various aspects of network codingwith dynamic redundancy overhead as described herein. For example, thecommunications manager 1020, the receiver 1010, the transmitter 1015, orvarious combinations or components thereof may support a method forperforming one or more of the functions described herein.

In some examples, the communications manager 1020, the receiver 1010,the transmitter 1015, or various combinations or components thereof maybe implemented in hardware (e.g., in communications managementcircuitry). The hardware may include a processor, a digital signalprocessor (DSP), an application-specific integrated circuit (ASIC), anFPGA, or other programmable logic device, a discrete gate or transistorlogic, discrete hardware components, or any combination thereofconfigured as or otherwise supporting a means for performing thefunctions described in the present disclosure. In some examples, aprocessor and memory coupled with the processor may be configured toperform one or more of the functions described herein (e.g., byexecuting, by the processor, instructions stored in the memory).

Additionally or alternatively, in some examples, the communicationsmanager 1020, the receiver 1010, the transmitter 1015, or variouscombinations or components thereof may be implemented in code (e.g., ascommunications management software or firmware) executed by a processor.If implemented in code executed by a processor, the functions of thecommunications manager 1020, the receiver 1010, the transmitter 1015, orvarious combinations or components thereof may be performed by ageneral-purpose processor, a DSP, a central processing unit (CPU), anASIC, an FPGA, or any combination of these or other programmable logicdevices (e.g., configured as or otherwise supporting a means forperforming the functions described in the present disclosure).

In some examples, the communications manager 1020 may be configured toperform various operations (e.g., receiving, monitoring, transmitting)using or otherwise in cooperation with the receiver 1010, thetransmitter 1015, or both. For example, the communications manager 1020may receive information from the receiver 1010, send information to thetransmitter 1015, or be integrated in combination with the receiver1010, the transmitter 1015, or both to receive information, transmitinformation, or perform various other operations as described herein.

The communications manager 1020 may support wireless communication at aUE in accordance with examples as disclosed herein. For example, thecommunications manager 1020 may be configured as or otherwise support ameans for receiving, from a base station, a first set of network codingencoded packets including a first redundancy overhead. Thecommunications manager 1020 may be configured as or otherwise support ameans for determining a failure rate associated with the first set ofnetwork coding encoded packets. The communications manager 1020 may beconfigured as or otherwise support a means for transmitting, to the basestation, a message related to a second redundancy overhead based on thedetermined failure rate, where the second redundancy overhead isdifferent from the first redundancy overhead. The communications manager1020 may be configured as or otherwise support a means for receiving,from the base station and based on transmitting the message, one or moresecond sets of network coding encoded packets transmitted with thesecond redundancy overhead.

By including or configuring the communications manager 1020 inaccordance with examples as described herein, the device 1005 (e.g., aprocessor controlling or otherwise coupled to the receiver 1010, thetransmitter 1015, the communications manager 1020, or a combinationthereof) may support techniques for more efficient utilization ofcommunication resources while maintaining reliable communications. Thatis, the communications manager 1020 may be configured to request forupdated redundancy overhead based on a channel quality, which maydecrease a likelihood of excessive redundancy overhead (e.g., resultingin less efficient utilization of communication resources) andinsufficient redundancy overhead (e.g., resulting in less reliablecommunications).

FIG. 11 shows a block diagram 1100 of a device 1105 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The device 1105 may be an example ofaspects of a device 1005 or a UE 115 as described herein. The device1105 may include a receiver 1110, a transmitter 1115, and acommunications manager 1120. The device 1105 may also include aprocessor. Each of these components may be in communication with oneanother (e.g., via one or more buses).

The receiver 1110 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to network coding withdynamic redundancy overhead). Information may be passed on to othercomponents of the device 1105. The receiver 1110 may utilize a singleantenna or a set of multiple antennas.

The transmitter 1115 may provide a means for transmitting signalsgenerated by other components of the device 1105. For example, thetransmitter 1115 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to network coding with dynamic redundancy overhead). Insome examples, the transmitter 1115 may be co-located with a receiver1110 in a transceiver module. The transmitter 1115 may utilize a singleantenna or a set of multiple antennas.

The device 1105, or various components thereof, may be an example ofmeans for performing various aspects of network coding with dynamicredundancy overhead as described herein. For example, the communicationsmanager 1120 may include a packet receiver 1125, a failure ratecomponent 1130, a message transmitter 1135, or any combination thereof.The communications manager 1120 may be an example of aspects of acommunications manager 1020 as described herein. In some examples, thecommunications manager 1120, or various components thereof, may beconfigured to perform various operations (e.g., receiving, monitoring,transmitting) using or otherwise in cooperation with the receiver 1110,the transmitter 1115, or both. For example, the communications manager1120 may receive information from the receiver 1110, send information tothe transmitter 1115, or be integrated in combination with the receiver1110, the transmitter 1115, or both to receive information, transmitinformation, or perform various other operations as described herein.

The communications manager 1120 may support wireless communication at aUE in accordance with examples as disclosed herein. The packet receiver1125 may be configured as or otherwise support a means for receiving,from a base station, a first set of network coding encoded packetsincluding a first redundancy overhead. The failure rate component 1130may be configured as or otherwise support a means for determining afailure rate associated with the first set of network coding encodedpackets. The message transmitter 1135 may be configured as or otherwisesupport a means for transmitting, to the base station, a message relatedto a second redundancy overhead based on the determined failure rate,where the second redundancy overhead is different from the firstredundancy overhead. The packet receiver 1125 may be configured as orotherwise support a means for receiving, from the base station and basedon transmitting the message, one or more second sets of network codingencoded packets transmitted with the second redundancy overhead.

FIG. 12 shows a block diagram 1200 of a communications manager 1220 thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure. The communications manager 1220may be an example of aspects of a communications manager 1020, acommunications manager 1120, or both, as described herein. Thecommunications manager 1220, or various components thereof, may be anexample of means for performing various aspects of network coding withdynamic redundancy overhead as described herein. For example, thecommunications manager 1220 may include a packet receiver 1225, afailure rate component 1230, a message transmitter 1235, a controlmessage receiver 1240, or any combination thereof. Each of thesecomponents may communicate, directly or indirectly, with one another(e.g., via one or more buses).

The communications manager 1220 may support wireless communication at aUE in accordance with examples as disclosed herein. The packet receiver1225 may be configured as or otherwise support a means for receiving,from a base station, a first set of network coding encoded packetsincluding a first redundancy overhead. The failure rate component 1230may be configured as or otherwise support a means for determining afailure rate associated with the first set of network coding encodedpackets. The message transmitter 1235 may be configured as or otherwisesupport a means for transmitting, to the base station, a message relatedto a second redundancy overhead based on the determined failure rate,where the second redundancy overhead is different from the firstredundancy overhead. In some examples, the packet receiver 1225 may beconfigured as or otherwise support a means for receiving, from the basestation and based on transmitting the message, one or more second setsof network coding encoded packets transmitted with the second redundancyoverhead.

In some examples, to support transmitting the message related to thesecond redundancy overhead, the message transmitter 1235 may beconfigured as or otherwise support a means for transmitting a request toupdate the first redundancy overhead to the second redundancy overheadfor the one or more second sets of network coding encoded packets.

In some examples, the failure rate component 1230 may be configured asor otherwise support a means for identifying that the failure rateassociated with the first set of network coding encoded packets exceedsa threshold failure rate, where transmitting the request to update thefirst redundancy overhead is based on the failure rate exceeding thethreshold failure rate.

In some examples, to support transmitting the request to update thefirst redundancy overhead, the message transmitter 1235 may beconfigured as or otherwise support a means for transmitting the requestto update the first redundancy overhead periodically and in accordancewith a periodicity for updating redundancy overheads.

In some examples, the control message receiver 1240 may be configured asor otherwise support a means for receiving, from the base station, aradio resource control message indicating one or more of a periodicityfor updating redundancy overheads and a threshold failure rateassociated with updating redundancy overheads, where the request toupdate the first redundancy overhead is in accordance with the radioresource control message.

In some examples, to support transmitting the message related to thesecond redundancy overhead, the message transmitter 1235 may beconfigured as or otherwise support a means for transmitting the messagevia a medium access control-control element or uplink controlinformation.

In some examples, the message related to the second redundancy overheadincludes an indication of the failure rate associated with the first setof network coding encoded packets.

In some examples, to support determining the failure rate, the failurerate component 1230 may be configured as or otherwise support a meansfor attempting to receive each of the first set of network codingencoded packets. In some examples, to support determining the failurerate, the failure rate component 1230 may be configured as or otherwisesupport a means for estimating the failure rate based on a quantity ofthe first set of network coding encoded packets that are successfullyreceived when attempting to receive each of the first set of networkcoding encoded packets.

In some examples, to support determining the failure rate, the failurerate component 1230 may be configured as or otherwise support a meansfor identifying a quantity of the first set of network coding encodedpackets that are received via an RLC entity at the UE. In some examples,to support determining the failure rate, the failure rate component 1230may be configured as or otherwise support a means for estimating thefailure rate based on the quantity of the first set of network codingencoded packets that are received via the RLC entity.

FIG. 13 shows a diagram of a system 1300 including a device 1305 thatsupports network coding with dynamic redundancy overhead in accordancewith aspects of the present disclosure. The device 1305 may be anexample of or include the components of a device 1005, a device 1105, ora UE 115 as described herein. The device 1305 may communicate wirelesslywith one or more base stations 105, UEs 115, or any combination thereof.The device 1305 may include components for bi-directional voice and datacommunications including components for transmitting and receivingcommunications, such as a communications manager 1320, an input/output(I/O) controller 1310, a transceiver 1315, an antenna 1325, a memory1330, code 1335, and a processor 1340. These components may be inelectronic communication or otherwise coupled (e.g., operatively,communicatively, functionally, electronically, electrically) via one ormore buses (e.g., a bus 1345).

The I/O controller 1310 may manage input and output signals for thedevice 1305. The I/O controller 1310 may also manage peripherals notintegrated into the device 1305. In some cases, the I/O controller 1310may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 1310 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, oranother known operating system. Additionally or alternatively, the I/Ocontroller 1310 may represent or interact with a modem, a keyboard, amouse, a touchscreen, or a similar device. In some cases, the I/Ocontroller 1310 may be implemented as part of a processor, such as theprocessor 1340. In some cases, a user may interact with the device 1305via the I/O controller 1310 or via hardware components controlled by theI/O controller 1310.

In some cases, the device 1305 may include a single antenna 1325.However, in some other cases, the device 1305 may have more than oneantenna 1325, which may be capable of concurrently transmitting orreceiving multiple wireless transmissions. The transceiver 1315 maycommunicate bi-directionally, via the one or more antennas 1325, wired,or wireless links as described herein. For example, the transceiver 1315may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 1315may also include a modem to modulate the packets, to provide themodulated packets to one or more antennas 1325 for transmission, and todemodulate packets received from the one or more antennas 1325. Thetransceiver 1315, or the transceiver 1315 and one or more antennas 1325,may be an example of a transmitter 1015, a transmitter 1115, a receiver1010, a receiver 1110, or any combination thereof or component thereof,as described herein.

The memory 1330 may include RAM and ROM. The memory 1330 may storecomputer-readable, computer-executable code 1335 including instructionsthat, when executed by the processor 1340, cause the device 1305 toperform various functions described herein. The code 1335 may be storedin a non-transitory computer-readable medium such as system memory oranother type of memory. In some cases, the code 1335 may not be directlyexecutable by the processor 1340 but may cause a computer (e.g., whencompiled and executed) to perform functions described herein. In somecases, the memory 1330 may contain, among other things, a BIOS which maycontrol basic hardware or software operation such as the interactionwith peripheral components or devices.

The processor 1340 may include an intelligent hardware device (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1340 may be configured to operate a memoryarray using a memory controller. In some other cases, a memorycontroller may be integrated into the processor 1340. The processor 1340may be configured to execute computer-readable instructions stored in amemory (e.g., the memory 1330) to cause the device 1305 to performvarious functions (e.g., functions or tasks supporting network codingwith dynamic redundancy overhead). For example, the device 1305 or acomponent of the device 1305 may include a processor 1340 and memory1330 coupled to the processor 1340, the processor 1340 and memory 1330configured to perform various functions described herein.

The communications manager 1320 may support wireless communication at aUE in accordance with examples as disclosed herein. For example, thecommunications manager 1320 may be configured as or otherwise support ameans for receiving, from a base station, a first set of network codingencoded packets including a first redundancy overhead. Thecommunications manager 1320 may be configured as or otherwise support ameans for determining a failure rate associated with the first set ofnetwork coding encoded packets. The communications manager 1320 may beconfigured as or otherwise support a means for transmitting, to the basestation, a message related to a second redundancy overhead based on thedetermined failure rate, where the second redundancy overhead isdifferent from the first redundancy overhead. The communications manager1320 may be configured as or otherwise support a means for receiving,from the base station and based on transmitting the message, one or moresecond sets of network coding encoded packets transmitted with thesecond redundancy overhead.

By including or configuring the communications manager 1320 inaccordance with examples as described herein, the device 1305 maysupport techniques for improved communication reliability and moreefficient utilization of communication resources. That is, thecommunications manager 1320 may be configured to request for updatedredundancy overhead based on a channel quality, which may decrease alikelihood of excessive redundancy overhead (e.g., resulting in lessefficient utilization of communication resources) and insufficientredundancy overhead (e.g., resulting in less reliable communications).

In some examples, the communications manager 1320 may be configured toperform various operations (e.g., receiving, monitoring, transmitting)using or otherwise in cooperation with the transceiver 1315, the one ormore antennas 1325, or any combination thereof. Although thecommunications manager 1320 is illustrated as a separate component, insome examples, one or more functions described with reference to thecommunications manager 1320 may be supported by or performed by theprocessor 1340, the memory 1330, the code 1335, or any combinationthereof. For example, the code 1335 may include instructions executableby the processor 1340 to cause the device 1305 to perform variousaspects of network coding with dynamic redundancy overhead as describedherein, or the processor 1340 and the memory 1330 may be otherwiseconfigured to perform or support such operations.

FIG. 14 shows a flowchart illustrating a method 1400 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The operations of the method 1400 maybe implemented by a base station or its components as described herein.For example, the operations of the method 1400 may be performed by abase station 105 as described with reference to FIGS. 1 through 9. Insome examples, a base station may execute a set of instructions tocontrol the functional elements of the base station to perform thedescribed functions. Additionally or alternatively, the base station mayperform aspects of the described functions using special-purposehardware.

At 1405, the method may include determining a failure rate associatedwith a transmission of a first set of network coding encoded packets toa UE. The operations of 1405 may be performed in accordance withexamples as disclosed herein. In some examples, aspects of theoperations of 1405 may be performed by a failure rate manager 825 asdescribed with reference to FIG. 8.

At 1410, the method may include identifying a redundancy overheadassociated with one or more second sets of network coding encodedpackets for the UE based on the failure rate associated with thetransmission of the first set of network coding encoded packets to theUE. The operations of 1410 may be performed in accordance with examplesas disclosed herein. In some examples, aspects of the operations of 1410may be performed by a redundancy overhead manager 830 as described withreference to FIG. 8.

At 1415, the method may include transmitting the one or more second setsof network coding encoded packets to the UE, the one or more second setsof network coding encoded packets being transmitted using the identifiedredundancy overhead. The operations of 1415 may be performed inaccordance with examples as disclosed herein. In some examples, aspectsof the operations of 1415 may be performed by a packet transmitter 835as described with reference to FIG. 8.

FIG. 15 shows a flowchart illustrating a method 1500 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The operations of the method 1500 maybe implemented by a base station or its components as described herein.For example, the operations of the method 1500 may be performed by abase station 105 as described with reference to FIGS. 1 through 9. Insome examples, a base station may execute a set of instructions tocontrol the functional elements of the base station to perform thedescribed functions. Additionally or alternatively, the base station mayperform aspects of the described functions using special-purposehardware.

At 1505, the method may include determining a failure rate associatedwith a transmission of a first set of network coding encoded packets toa UE. The operations of 1505 may be performed in accordance withexamples as disclosed herein. In some examples, aspects of theoperations of 1505 may be performed by a failure rate manager 825 asdescribed with reference to FIG. 8.

At 1510, the method may include identifying that the failure rateassociated with the transmission of the first set of network codingencoded packets to the UE exceeds a threshold failure rate. Theoperations of 1510 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1510may be performed by a redundancy overhead manager 830 as described withreference to FIG. 8.

At 1515, the method may include determining a redundancy overheadassociated with one or more second sets of network coding encodedpackets for the UE based on the failure rate exceeding the thresholdfailure rate. The operations of 1515 may be performed in accordance withexamples as disclosed herein. In some examples, aspects of theoperations of 1515 may be performed by a redundancy overhead manager 830as described with reference to FIG. 8.

At 1520, the method may include transmitting the one or more second setsof network coding encoded packets to the UE, the one or more second setsof network coding encoded packets being transmitted using the identifiedredundancy overhead. The operations of 1520 may be performed inaccordance with examples as disclosed herein. In some examples, aspectsof the operations of 1520 may be performed by a packet transmitter 835as described with reference to FIG. 8.

FIG. 16 shows a flowchart illustrating a method 1600 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The operations of the method 1600 maybe implemented by a UE or its components as described herein. Forexample, the operations of the method 1600 may be performed by a UE 115as described with reference to FIGS. 1 through 5 and 10 through 13. Insome examples, a UE may execute a set of instructions to control thefunctional elements of the UE to perform the described functions.Additionally or alternatively, the UE may perform aspects of thedescribed functions using special-purpose hardware.

At 1605, the method may include receiving, from a base station, a firstset of network coding encoded packets including a first redundancyoverhead. The operations of 1605 may be performed in accordance withexamples as disclosed herein. In some examples, aspects of theoperations of 1605 may be performed by a packet receiver 1225 asdescribed with reference to FIG. 12.

At 1610, the method may include determining a failure rate associatedwith the first set of network coding encoded packets. The operations of1610 may be performed in accordance with examples as disclosed herein.In some examples, aspects of the operations of 1610 may be performed bya failure rate component 1230 as described with reference to FIG. 12.

At 1615, the method may include transmitting, to the base station, amessage related to a second redundancy overhead based on the determinedfailure rate, where the second redundancy overhead is different from thefirst redundancy overhead. For example, the message may be a request toupdate the first redundancy overhead to the second redundancy overheadfor the one or more second sets of network coding encoded packets. Inanother example, the message may include an indication of the failurerate associated with the first set of network coding encoded packets(e.g., transmitted via a MAC-CE or UCI). In some cases, the method mayadditionally include transmitting, to the base station, a report. Forexample, the report could be HARQ NACK feedback for the first set ofnetwork coding encoded packets. In another example, the report could bean RLC retransmission request for RLC entities. The operations of 1615may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 1615 may be performed by amessage transmitter 1235 as described with reference to FIG. 12.

At 1620, the method may include receiving, from the base station andbased on transmitting the message, one or more second sets of networkcoding encoded packets transmitted with the second redundancy overhead.The operations of 1620 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1620may be performed by a packet receiver 1225 as described with referenceto FIG. 12.

FIG. 17 shows a flowchart illustrating a method 1700 that supportsnetwork coding with dynamic redundancy overhead in accordance withaspects of the present disclosure. The operations of the method 1700 maybe implemented by a UE or its components as described herein. Forexample, the operations of the method 1700 may be performed by a UE 115as described with reference to FIGS. 1 through 5 and 10 through 13. Insome examples, a UE may execute a set of instructions to control thefunctional elements of the UE to perform the described functions.Additionally or alternatively, the UE may perform aspects of thedescribed functions using special-purpose hardware.

At 1705, the method may include receiving, from a base station, a firstset of network coding encoded packets including a first redundancyoverhead. The operations of 1705 may be performed in accordance withexamples as disclosed herein. In some examples, aspects of theoperations of 1705 may be performed by a packet receiver 1225 asdescribed with reference to FIG. 12.

At 1710, the method may include determining a failure rate associatedwith the first set of network coding encoded packets. The operations of1710 may be performed in accordance with examples as disclosed herein.In some examples, aspects of the operations of 1710 may be performed bya failure rate component 1230 as described with reference to FIG. 12.

At 1715, the method may include transmitting, to the base station, arequest to update the first redundancy overhead to a second redundancyoverhead (e.g., different than the first redundancy overhead) for theone or more second sets of network coding encoded packets. Theoperations of 1715 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1715may be performed by a message transmitter 1235 as described withreference to FIG. 12.

At 1720, the method may include receiving, from the base station andbased on transmitting the message, one or more second sets of networkcoding encoded packets transmitted with the second redundancy overhead.The operations of 1720 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1720may be performed by a packet receiver 1225 as described with referenceto FIG. 12.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a base station,comprising: determining a failure rate associated with a transmission ofa first set of network coding encoded packets to a UE; identifying aredundancy overhead associated with one or more second sets of networkcoding encoded packets for the UE based at least in part on the failurerate associated with the transmission of the first set of network codingencoded packets to the UE; and transmitting the one or more second setsof network coding encoded packets to the UE, the one or more second setsof network coding encoded packets being transmitted using the identifiedredundancy overhead.

Aspect 2: The method of aspect 1, wherein identifying the redundancyoverhead further comprises: identifying that the failure rate associatedwith the transmission of the first set of network coding encoded packetsto the UE exceeds a threshold failure rate; and determining theredundancy overhead based at least in part on the failure rate exceedingthe threshold failure rate.

Aspect 3: The method of any of aspects 1 and 2, wherein identifying theredundancy overhead further comprises: identifying the redundancyoverhead periodically and in accordance with a periodicity foridentifying redundancy overheads.

Aspect 4: The method of any of aspects 1 through 3, wherein identifyingthe redundancy overhead further comprises: identifying the redundancyoverhead in response to a first message, received from the UE,requesting an updated redundancy overhead for the one or more secondsets of network coding encoded packets.

Aspect 5: The method of aspect 4, further comprising: transmitting, tothe UE, a RRC message indicating one or more of a periodicity forupdating redundancy overheads and a threshold failure rate associatedwith updating redundancy overheads, wherein the first message is inaccordance with the RRC message.

Aspect 6: The method of any of aspects 4 and 5, further comprising:receiving, in the first message, an indication of the failure rate,wherein determining the failure rate associated with the transmission ofthe first set of network coding encoded packets to the UE is based atleast in part on the indication of the failure rate.

Aspect 7: The method of any of aspects 4 through 6, further comprising:receiving the first message via a MAC-CE or UCI.

Aspect 8: The method of any of aspects 1 through 7, further comprising:receiving a first message from the UE in response to the transmission ofthe first set of network coding encoded packets to the UE, whereindetermining the failure rate is based at least in part on the firstmessage.

Aspect 9: The method of aspect 8, wherein the first message is afeedback message or a retransmission request associated with thetransmission of the first set of network coding encoded packets; anddetermining the failure rate comprises estimating the failure rate basedat least in part on the feedback message or the retransmission request.

Aspect 10: The method of aspect 9, wherein the feedback message is aHARQ NACK feedback message.

Aspect 11: The method of any of aspect 9, wherein the retransmissionrequest is a RLC status report message.

Aspect 12: The method of any of aspects 8 through 11, wherein the firstmessage comprises an indication of the failure rate; and the determinedfailure rate is the indicated failure rate.

Aspect 13: The method of any of aspects 1 through 12, furthercomprising: transmitting the first set of network coding encoded packetsto the UE comprising an initial redundancy overhead different from theidentified redundancy overhead, wherein determining the failure rate isbased at least in part on transmitting the first set of network codingencoded packets to the UE.

Aspect 14: The method of any of aspects 1 through 13, furthercomprising: transmitting a third set of network coding encoded packetsto a second UE different from the UE, wherein the third set of networkcoding encoded packets comprises a second redundancy overhead differentfrom the identified redundancy overhead.

Aspect 15: A method for wireless communication at a UE, comprising:receiving, from a base station, a first set of network coding encodedpackets comprising a first redundancy overhead; determining a failurerate associated with the first set of network coding encoded packets;transmitting, to the base station, a message related to a secondredundancy overhead based at least in part on the determined failurerate, wherein the second redundancy overhead is different from the firstredundancy overhead; and receiving, from the base station and based atleast in part on transmitting the message, one or more second sets ofnetwork coding encoded packets transmitted with the second redundancyoverhead.

Aspect 16: The method of aspect 15, wherein transmitting the messagerelated to the second redundancy overhead comprises: transmitting arequest to update the first redundancy overhead to the second redundancyoverhead for the one or more second sets of network coding encodedpackets.

Aspect 17: The method of aspect 16, further comprising: identifying thatthe failure rate associated with the first set of network coding encodedpackets exceeds a threshold failure rate, wherein transmitting therequest to update the first redundancy overhead is based at least inpart on the failure rate exceeding the threshold failure rate.

Aspect 18: The method of any of aspects 16 and 17, wherein transmittingthe request to update the first redundancy overhead comprises:transmitting the request to update the first redundancy overheadperiodically and in accordance with a periodicity for updatingredundancy overheads.

Aspect 19: The method of any of aspects 16 through 18, furthercomprising: receiving, from the base station, a RRC message indicatingone or more of a periodicity for updating redundancy overheads and athreshold failure rate associated with updating redundancy overheads,wherein the request to update the first redundancy overhead is inaccordance with the RRC message.

Aspect 20: The method of any of aspects 15 through 19, whereintransmitting the message related to the second redundancy overheadcomprises: transmitting the message via a MAC-CE or UCI.

Aspect 21: The method of any of aspects 15 through 20, wherein themessage related to the second redundancy overhead comprises anindication of the failure rate associated with the first set of networkcoding encoded packets.

Aspect 22: The method of any of aspects 15 through 21, whereindetermining the failure rate comprises: attempting to receive each ofthe first set of network coding encoded packets; and estimating thefailure rate based at least in part on a quantity of the first set ofnetwork coding encoded packets that are successfully received whenattempting to receive each of the first set of network coding encodedpackets.

Aspect 23: The method of any of aspects 15 through 22, whereindetermining the failure rate comprises: identifying a quantity of thefirst set of network coding encoded packets that are received via a RLCentity at the UE; and estimating the failure rate based at least in parton the quantity of the first set of network coding encoded packets thatare received via the RLC entity.

Aspect 24: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 1 through 14.

Aspect 25: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects1 through 14.

Aspect 26: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 1 through 14.

Aspect 27: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 15 through 23.

Aspect 28: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 15 through23.

Aspect 29: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 15through 23.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may bedescribed for purposes of example, and LTE, LTE-A, LTE-A Pro, or NRterminology may be used in much of the description, the techniquesdescribed herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NRnetworks. For example, the described techniques may be applicable tovarious other wireless communications systems such as Ultra MobileBroadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, aswell as other systems and radio technologies not explicitly mentionedherein.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, a CPU, an FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices (e.g., acombination of a DSP and a microprocessor, multiple microprocessors, oneor more microprocessors in conjunction with a DSP core, or any othersuch configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein may be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that may beaccessed by a general-purpose or special-purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude RAM, ROM, electrically erasable programmable ROM (EEPROM), flashmemory, compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that may be used to carry or store desired programcode means in the form of instructions or data structures and that maybe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of computer-readable medium. Disk and disc,as used herein, include CD, laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an example step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “example” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, known structures and devices are shown inblock diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person having ordinaryskill in the art to make or use the disclosure. Various modifications tothe disclosure will be apparent to a person having ordinary skill in theart, and the generic principles defined herein may be applied to othervariations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described hereinbut is to be accorded the broadest scope consistent with the principlesand novel features disclosed herein.

What is claimed is:
 1. A method for wireless communication at a basestation, comprising: determining a failure rate associated with atransmission of a first set of network coding encoded packets to a userequipment (UE); identifying a redundancy overhead associated with one ormore second sets of network coding encoded packets for the UE based atleast in part on the failure rate associated with the transmission ofthe first set of network coding encoded packets to the UE; andtransmitting the one or more second sets of network coding encodedpackets to the UE, the one or more second sets of network coding encodedpackets being transmitted using the identified redundancy overhead. 2.The method of claim 1, wherein identifying the redundancy overheadfurther comprises: identifying that the failure rate associated with thetransmission of the first set of network coding encoded packets to theUE exceeds a threshold failure rate; and determining the redundancyoverhead based at least in part on the failure rate exceeding thethreshold failure rate.
 3. The method of claim 1, wherein identifyingthe redundancy overhead further comprises: identifying the redundancyoverhead periodically and in accordance with a periodicity foridentifying redundancy overheads.
 4. The method of claim 1, whereinidentifying the redundancy overhead further comprises: identifying theredundancy overhead in response to a first message, received from theUE, requesting an updated redundancy overhead for the one or more secondsets of network coding encoded packets.
 5. The method of claim 4,further comprising: transmitting, to the UE, a radio resource controlmessage indicating one or more of a periodicity for updating redundancyoverheads and a threshold failure rate associated with updatingredundancy overheads, wherein the first message is in accordance withthe radio resource control message.
 6. The method of claim 4, furthercomprising: receiving, in the first message, an indication of thefailure rate, wherein determining the failure rate associated with thetransmission of the first set of network coding encoded packets to theUE is based at least in part on the indication of the failure rate. 7.The method of claim 4, further comprising: receiving the first messagevia a medium access control-control element or uplink controlinformation.
 8. The method of claim 1, further comprising: receiving afirst message from the UE in response to the transmission of the firstset of network coding encoded packets to the UE, wherein determining thefailure rate is based at least in part on the first message.
 9. Themethod of claim 8, wherein: the first message is a feedback message or aretransmission request associated with the transmission of the first setof network coding encoded packets; and determining the failure ratecomprises estimating the failure rate based at least in part on thefeedback message or the retransmission request.
 10. The method of claim9, wherein the feedback message is a hybrid automatic repeat requestnegative acknowledgement feedback message.
 11. The method of claim 9,wherein the retransmission request is a radio link control status reportmessage.
 12. The method of claim 8, wherein: the first message comprisesan indication of the failure rate; and the determined failure rate isthe indicated failure rate.
 13. The method of claim 1, furthercomprising: transmitting the first set of network coding encoded packetsto the UE comprising an initial redundancy overhead different from theidentified redundancy overhead, wherein determining the failure rate isbased at least in part on transmitting the first set of network codingencoded packets to the UE.
 14. The method of claim 1, furthercomprising: transmitting a third set of network coding encoded packetsto a second UE different from the UE, wherein the third set of networkcoding encoded packets comprises a second redundancy overhead differentfrom the identified redundancy overhead.
 15. A method for wirelesscommunication at a user equipment (UE), comprising: receiving, from abase station, a first set of network coding encoded packets comprising afirst redundancy overhead; determining a failure rate associated withthe first set of network coding encoded packets; transmitting, to thebase station, a message related to a second redundancy overhead based atleast in part on the determined failure rate, wherein the secondredundancy overhead is different from the first redundancy overhead; andreceiving, from the base station and based at least in part ontransmitting the message, one or more second sets of network codingencoded packets transmitted with the second redundancy overhead.
 16. Themethod of claim 15, wherein transmitting the message related to thesecond redundancy overhead comprises: transmitting a request to updatethe first redundancy overhead to the second redundancy overhead for theone or more second sets of network coding encoded packets.
 17. Themethod of claim 16, further comprising: identifying that the failurerate associated with the first set of network coding encoded packetsexceeds a threshold failure rate, wherein transmitting the request toupdate the first redundancy overhead is based at least in part on thefailure rate exceeding the threshold failure rate.
 18. The method ofclaim 16, wherein transmitting the request to update the firstredundancy overhead comprises: transmitting the request to update thefirst redundancy overhead periodically and in accordance with aperiodicity for updating redundancy overheads.
 19. The method of claim16, further comprising: receiving, from the base station, a radioresource control message indicating one or more of a periodicity forupdating redundancy overheads and a threshold failure rate associatedwith updating redundancy overheads, wherein the request to update thefirst redundancy overhead is in accordance with the radio resourcecontrol message.
 20. The method of claim 15, wherein transmitting themessage related to the second redundancy overhead comprises:transmitting the message via a medium access control-control element oruplink control information.
 21. The method of claim 15, wherein themessage related to the second redundancy overhead comprises anindication of the failure rate associated with the first set of networkcoding encoded packets.
 22. The method of claim 15, wherein determiningthe failure rate comprises: attempting to receive each of the first setof network coding encoded packets; and estimating the failure rate basedat least in part on a quantity of the first set of network codingencoded packets that are successfully received when attempting toreceive each of the first set of network coding encoded packets.
 23. Themethod of claim 15, wherein determining the failure rate comprises:identifying a quantity of the first set of network coding encodedpackets that are received via a radio link control entity at the UE; andestimating the failure rate based at least in part on the quantity ofthe first set of network coding encoded packets that are received viathe radio link control entity.
 24. An apparatus for wirelesscommunication at a base station, comprising: a processor; memory coupledwith the processor; and instructions stored in the memory and executableby the processor to cause the apparatus to: determine a failure rateassociated with a transmission of a first set of network coding encodedpackets to a user equipment (UE); identify a redundancy overheadassociated with one or more second sets of network coding encodedpackets for the UE based at least in part on the failure rate associatedwith the transmission of the first set of network coding encoded packetsto the UE; and transmit the one or more second sets of network codingencoded packets to the UE, the one or more second sets of network codingencoded packets being transmitted using the identified redundancyoverhead.
 25. The apparatus of claim 24, wherein the instructions toidentify the redundancy overhead are further executable by the processorto cause the apparatus to: identify that the failure rate associatedwith the transmission of the first set of network coding encoded packetsto the UE exceeds a threshold failure rate; and determine the redundancyoverhead based at least in part on the failure rate exceeding thethreshold failure rate.
 26. The apparatus of claim 24, wherein theinstructions to identify the redundancy overhead are further executableby the processor to cause the apparatus to: identify the redundancyoverhead periodically and in accordance with a periodicity foridentifying redundancy overheads.
 27. The apparatus of claim 24, whereinthe instructions to identify the redundancy overhead are furtherexecutable by the processor to cause the apparatus to: identify theredundancy overhead in response to a first message, received from theUE, requesting an updated redundancy overhead for the one or more secondsets of network coding encoded packets.
 28. An apparatus for wirelesscommunication at a user equipment (UE), comprising: a processor; memorycoupled with the processor; and instructions stored in the memory andexecutable by the processor to cause the apparatus to: receive, from abase station, a first set of network coding encoded packets comprising afirst redundancy overhead; determine a failure rate associated with thefirst set of network coding encoded packets; transmit, to the basestation, a message related to a second redundancy overhead based atleast in part on the determined failure rate, wherein the secondredundancy overhead is different from the first redundancy overhead; andreceive, from the base station and based at least in part ontransmitting the message, one or more second sets of network codingencoded packets transmitted with the second redundancy overhead.
 29. Theapparatus of claim 28, wherein the instructions to transmit the messagerelated to the second redundancy overhead are executable by theprocessor to cause the apparatus to: transmit a request to update thefirst redundancy overhead to the second redundancy overhead for the oneor more second sets of network coding encoded packets.
 30. The apparatusof claim 29, wherein the instructions are further executable by theprocessor to cause the apparatus to: identify that the failure rateassociated with the first set of network coding encoded packets exceedsa threshold failure rate, wherein transmitting the request to update thefirst redundancy overhead is based at least in part on the failure rateexceeding the threshold failure rate.